Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1609

reference
539-tree-1
name
1609
tree-preservation-order

undefined

539-tpo-1
uprn
address-text
point
POINT (-1.023000 50.884124)
geometry
MULTIPOLYGON (((-1.022943 50.884118,-1.022946 50.884129,-1.022953 50.884139,-1.022966 50.884148,-1.022982 50.884153,-1.022999 50.884155,-1.023017 50.884153,-1.023033 50.884148,-1.023045 50.884140,-1.023054 50.884130,-1.023057 50.884119,-1.023054 50.884108,-1.023046 50.884098,-1.023034 50.884090,-1.023018 50.884085,-1.023001 50.884083,-1.022983 50.884084,-1.022967 50.884089,-1.022954 50.884097,-1.022946 50.884107,-1.022943 50.884118)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL